This is visualization of JUnit code history using d3.js. Produced with this IntelliJ plugin.
Change size chart
Shows amount of changes by day/week. The idea is to see overall trend of project.Amount of committers
Files changed in the same commit
This graph shows files which were changed in the same commit at least 7 times. Thickness of edges is proportional to the number of commits. Renamed and moved files are tracked but only current file name is displayed. The idea is to discover de facto dependencies between files.Committers changing same files
This graph shows committers and files. If file was edited by one committer and then edited by another within a week, a link is added. Links that happened at least 7 times are added to the graph. The is idea is to discover communication patterns and shared code "ownership".In this particular case graph is not very accurate because of different VCS user names for the same person (e.g. "dsaff" and "David Saff").
Amount of commits treemap
Shows a break-down of commits by package. Renamed and moved package are tracked but only current package name is displayed. The idea is to see which parts of the project have more attention (e.g. ration between changes in test and production code).Commit time punchcard
Shows amount of commits at certain time of day (this is similar to GitHub punchcard).Note that you can also group commits by minute (inspired by subsecond offset heatmaps).
Time between commits histogram
Shows histogram of time between commits by each committer.(If time between commits is less than 1 minute, it's discarded assuming it was a merge from pull request.)
Commit messages wordcloud
This is a word cloud from commit messages excluding some of prepositions and articles. The idea is to see what happened with code by observing human language.This particular cloud might not be very representative because of commit messages with meta-information (that's why cloud has "threeriversinstitute" in it). You can alt-click on words to exclude them.